Asynchronous custom exit points

ABSTRACT

The present technology may monitor an asynchronous transaction based on a custom exit point. Once an asynchronous method to be monitored has been identified, the transition framework may be tracked while executing the asynchronous method call. Within a .NET framework, monitoring may include tracking a task object, continuation method calls at the completion of a method, and tracking the continuation method as it executes other code. The asynchronous method may then be correlated within a business transaction using the returned task object data.

RELATED APPLICATION

This application is a continuation application of U.S. patent application Ser. No. 14/701,418, filed on Apr. 30, 2015, the entire content of which is incorporated herein.

BACKGROUND OF THE INVENTION

The World Wide Web has expanded to provide web services faster to consumers. Web services may be provided by a web application which uses one or more services to handle a transaction. The applications may be distributed over several machines, making the topology of the machines that provides the service more difficult to track and monitor.

A popular framework for providing a web is the .NET framework provided by Microsoft, Corp. In a .NET framework, certain transactions such as asynchronous transactions can be difficult to monitor. This is primarily due to the fact that a first thread may handle a first portion of a distributed business transaction, a second thread may handling another part of the distributed business transaction, and there is no connection or correlation between the two threads within the business transaction. What is needed is an improved manner for tracking asynchronous transactions.

SUMMARY OF THE CLAIMED INVENTION

The present technology may monitor asynchronous transactions over a different number of threads by capturing data and tracking transitions in the particular framework. Once an asynchronous method is called, the transition framework may be tracked while executing an asynchronous method call. Within a .NET framework, monitoring may include tracking a task object return, continuation method calls at the completion of a method, and tracking the continuation method as it executes other code. The asynchronous method may then be correlated within a business transaction using the returned task object data.

An embodiment may include a method for monitoring an asynchronous transaction. The method may detect an asynchronous method call within an application by an agent executing on a server. A task object associated with the method call may be monitored. The task object creation may be initiated by the asynchronous method call. Asynchronous method call data may be correlated with a distributed business transaction performed at least in part on the server.

An embodiment may include a system for monitoring a business transaction. The system may include a processor, a memory and one or more modules stored in memory and executable by the processor. When executed, the one or more modules may detect an asynchronous method call within an application by an agent executing on a server, monitor a task object associated with the method call, the task object creation initiated by the asynchronous method call, and correlate asynchronous method call data with a distributed business transaction performed at least in part on the server.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1A is a block diagram of a system for monitoring an asynchronous transaction based on a custom exit point.

FIG. 1B is a block diagram of a node.

FIG. 2 illustrates a method for monitoring an asynchronous transaction.

FIG. 3 illustrates a method for monitoring an asynchronous transition framework.

FIG. 4 illustrates a method for instrumenting an asynchronous method.

FIG. 5 illustrates block diagram of a computing system implementing the present technology.

DETAILED DESCRIPTION

The present technology may monitor an asynchronous transaction based on a custom exit point. Once an asynchronous method to be monitored has been identified, the transition framework may be tracked while executing the asynchronous method call. Within a .NET framework, monitoring may include tracking a task object, continuation method calls at the completion of a method, and tracking the continuation method as it executes other code. The asynchronous method may then be correlated within a business transaction using the returned task object data.

A .NET framework may include one or more IIS (Information Internet Server) web servers as well as additional servers. Each IIS server may include one or more applications and at least one additional server may include a coordinator. An application being monitored on an IIS server may include an agent and/or a profiler. The profiler may detect a call within or by the application and report the call to the coordinator. The coordinator may determine if the detected call is one that should be monitored, and informs the profiler appropriately. If the call should be monitored, an agent on the application monitors the call. In some instances, more or fewer modules than an agent and profiler may be used to monitor an application on a .NET framework. References to an agent and profiler are intended for purposes of example only.

One aspect of the present technology is that the asynchronous framework of the .NET application is monitored. In a .NET framework, an asynchronous method may be called as a task object. The method may be compiled in the .NET framework with a C# compiler. The .NET framework compiler may create a state machine and replace an await function with code that sets a continuation method. The present technology may instrument selected asynchronous methods, continuation constructor methods, task objects, and other framework aspects. When the task completes, the continuation method is called. Understanding the .NET framework and instrumenting it as it progresses allows the present technology to track a custom exit point formed by an asynchronous method performed within that framework.

FIG. 1A is a block diagram of a system for monitoring an asynchronous transaction based on a custom exit point. FIG. 1A includes client 110, network 120, network server 130, application server 140, server 150, controller 160, and client device 170. Client 110 may communicate with network server 130 over network 120. Client 110 may be any sort of computing device, such as for example a desktop computer, a work station, a lap top computer a mobile device such as a smart phone or a tablet computer, or some other computing device. Client 110 may include network browser 115 as well as other software. Network browser 115 may be stored on client 110 and executed by one or more processors to provide content through an output device of client 110. The content may be received from application server 140 via network server 130 and network 120. Client 110 may receive input from a user through network browser 115 and communicate with application server 140 to provide content to the user.

Network 120 may facilitate communication of data between different servers, devices and machines. The network may be implemented as a private network, public network, intranet, the Internet, a Wi-Fi network, cellular network, or a combination of these networks.

Network server 130 is connected to network 120 and may receive and process requests received over network 120. Network server 130 may be implemented as one or more servers implementing a network service. When network 120 is the Internet, network server 130 may be implemented as a web server. Network server 130 and application server 140 may be implemented on separate or the same server or machine.

Application server 140 may include one or more applications 142. Application server 140 may be implemented using one or more servers which communicate with network server 130, server 150, controller 160, and other devices. In some embodiments, network server 130 and application server 140 may be implemented as the same server.

Application 142 may be monitored by one or more agents (see FIG. 1B). Application 142 may execute in any of a number of frameworks, such as for example a JAVA framework, a .NET framework, or other framework. Application 142 is discussed in more detail below with respect to the method of FIG. 1B.

Server 150 may communicate with application servers 140 and controller 160. Server 150 may include a coordinator 152 and a configuration file 154. Coordinator 152 may manage a list of methods, calls, objects and other code that should be monitored. Configuration file 154 may be accessed by coordinator 152 and may include a list of nodes that may be monitored within the system of FIG. 1A. The list of nodes may be compiled automatically, based on user input, or based on other parameters.

Controller 160 may control and manage monitoring of business transactions distributed over application servers 130-160. Controller 160 may receive runtime data from agents and coordinators, associate portions of business transaction data, communicate with agents to configure collection of runtime data, and provide performance data and reporting through an interface. The interface may be viewed as a web-based interface viewable by client device 110. In some embodiments, a client device 170 may directly communicate with controller 160 to view an interface for monitoring data.

In some instances, controller 160 may install an agent into one or more application servers 140. Controller 160 may receive correlation configuration data, such as an object, a method, or class identifier, from a user through client device 170.

FIG. 1B is a block diagram of an application. Application 142 of FIG. 1B includes agent 144 and profiler 146.

Agent 144 may be installed on an application server by byte code instrumentation, downloading the application to the server, or in some other manner. Agent 144 may be executed to monitor an application, application server, a virtual machine, or other logical machine and may communicate with byte instrumented code on an application server, virtual machine 132 or another application or program on an application server. Agent 144 may detect operations such as receiving calls, creating objects, and sending requests by an application server, virtual machine, or logical machine. Agent 144 may insert instrumentation and receive data from instrumented code, process the data and transmit the data to controller 160. Agent 144 may perform other operations related to monitoring an application or logical machine as discussed herein. For example, agent 144 may identify other applications, share business transaction data, aggregate detected runtime data, and other operations.

Profiler 146 may detect when an application makes a call and may take actions based on that detection. Profiler 146 may be implemented within or outside of application 142 on an application server 140. Profiler 146 may communicate with coordinator 152 to determine if the application making the call should be monitored. In some instances, profiler 146 may implement byte code to activate an agent or cause an agent to be activated in case that the application should be monitored based on information received from coordinator 152.

FIG. 2 illustrates a method for monitoring an asynchronous transaction. A selection of a back-end calling method to monitor is received at step 210. The method that calls the back-end may provide an exit point from the current application to the external back-end. Subsequent monitoring of the selected method provides custom back-end monitoring within the current framework. The method may be selected based on user request, automated selection, or other means.

The selected method may be identified as an asynchronous method as step 220. In some instances, the present system may automatically determine if the selected method is an asynchronous method. For example, the system may detect a type “task” within the method, which in a .NET framework corresponds to an asynchronous method.

Next, the asynchronous transaction framework is monitored while executing the asynchronous method call at step 230. Monitoring the asynchronous transaction framework may include detecting operations of the framework, such as executing the asynchronous method, instrumenting asynchronous methods, instrumenting a continuation method, and other monitoring operations. More details for monitoring and asynchronous transaction framework are discussed with respect to the method of FIG. 3.

The back-end calling method is correlated with a business transaction at step 230. A first thread may be handling the asynchronous method identified at step 210. A second method may handle a task object that is executed as part of the asynchronous method. Data obtained from monitoring the asynchronous method and task object may be used to correlate the threads together as part of a distributed business transaction. More details for correlating are discussed with respect to the method of FIG. 4. Data regarding the performance of the business transaction is reported at step 240. The data may include asynchronous method call information as part of the end to end business transaction. The data may be reported as part of a call graph, trending data, graphics, and other means.

FIG. 3 illustrates a method for monitoring an asynchronous transition framework. The method of FIG. 3 provides more detail for step 220 of the method of FIG. 2. First, BCI is performed on the called asynchronous method at step 310. The instrumentation may include creating a new method that encompasses the asynchronous method to be monitored within a wrapper. The wrapper may include code for monitoring the start and end of the called method, collecting data for the method, and other monitoring actions. The instrumentation itself may include modifying a framework library and files. More detail for instrumenting the asynchronous method is discussed with respect to the method of FIG. 4.

Next, the instrumented asynchronous method is executed at step 320. A task object creation is detected at step 330 and the task object is instrumented at step 340. Task object instrumentation is used to correlate different threads associated with the asynchronous business transaction. For example, when the task object sends a call to the back-end, an identifier may be provided in the call. The identifier may be stored in the thread handling the asynchronous method in the .NET application, any thread used to process the completion of the call, and a thread or other code at the back-end server. The identifier may be used to correlate the threads involved with aspects of the asynchronous method on the .NET application as well as the remote back-end server.

At the completion of the synchronous method, a continuation method is called at step 350. The continuation method is instrumented at step 360. Instrumentation for the continuation method may result in data such as the time the continuation method is called, the recipient of the continuation method call, and other data. The instrumented continuation method may also provide results of the task object and details regarding code in the body of the asynchronous method which is executed by the continuation method after the task is complete at step 370. Data regarding the asynchronous method is then stored using the instrumented code at step 380.

FIG. 4 illustrates a method for instrumenting an asynchronous method. The method of FIG. 4 provides more detail for step 310 the method of FIG. 3.

Intermediate language (IL) is injected into a .NET framework library at step 410. The library may be an mscorlib.dll library within the .NET framework. The code inserted may include a code at the beginning and end of the asynchronous method, thereby providing a wrapper around the method.

A map is inserted into an AppDomain file at step 420. The map indicates a method begin pointer and method end pointer, both of which are expected to be part of the app domain. The AppDomain file may be part of the .NET framework and serve as a placeholder method.

An external dll is loaded with proper call backs at step 430. The proper call backs are used to fill the placeholder with the proper call back information. The map may be accessed with information regarding mapping call backs to a specific method.

FIG. 5 is a block diagram of a computer system for implementing the present technology. System 500 of FIG. 5 may be implemented in the contexts of the likes of clients 110 and 170, network server 130, servers 140-150, and controller 160.

The computing system 500 of FIG. 5 includes one or more processors 510 and memory 520. Main memory 520 stores, in part, instructions and data for execution by processor 510. Main memory 520 can store the executable code when in operation. The system 500 of FIG. 5 further includes a mass storage device 530, portable storage medium drive(s) 540, output devices 550, user input devices 560, a graphics display 570, and peripheral devices 580.

The components shown in FIG. 5 are depicted as being connected via a single bus 590. However, the components may be connected through one or more data transport means. For example, processor unit 510 and main memory 520 may be connected via a local microprocessor bus, and the mass storage device 530, peripheral device(s) 580, portable storage device 540, and display system 570 may be connected via one or more input/output (I/O) buses.

Mass storage device 530, which may be implemented with a magnetic disk drive or an optical disk drive, is a non-volatile storage device for storing data and instructions for use by processor unit 510. Mass storage device 530 can store the system software for implementing embodiments of the present invention for purposes of loading that software into main memory 520.

Portable storage device 540 operates in conjunction with a portable non-volatile storage medium, such as a floppy disk, compact disk or Digital video disc, to input and output data and code to and from the computer system 500 of FIG. 5. The system software for implementing embodiments of the present invention may be stored on such a portable medium and input to the computer system 500 via the portable storage device 540.

Input devices 560 provide a portion of a user interface. Input devices 560 may include an alpha-numeric keypad, such as a keyboard, for inputting alpha-numeric and other information, or a pointing device, such as a mouse, a trackball, stylus, or cursor direction keys. Additionally, the system 500 as shown in FIG. 5 includes output devices 550. Examples of suitable output devices include speakers, printers, network interfaces, and monitors.

Display system 570 may include a liquid crystal display (LCD) or other suitable display device. Display system 570 receives textual and graphical information, and processes the information for output to the display device.

Peripherals 580 may include any type of computer support device to add additional functionality to the computer system. For example, peripheral device(s) 580 may include a modem or a router.

The components contained in the computer system 500 of FIG. 5 are those typically found in computer systems that may be suitable for use with embodiments of the present invention and are intended to represent a broad category of such computer components that are well known in the art. Thus, the computer system 500 of FIG. 5 can be a personal computer, hand held computing device, telephone, mobile computing device, workstation, server, minicomputer, mainframe computer, or any other computing device. The computer can also include different bus configurations, networked platforms, multi-processor platforms, etc. Various operating systems can be used including Unix, Linux, Windows, Macintosh OS, Palm OS, Android OS, and other suitable operating systems.

When implementing a mobile device such as smart phone or tablet computer, the computer system 500 of FIG. 5 may include one or more antennas, radios, and other circuitry for communicating over wireless signals, such as for example communication using Wi-Fi, cellular, or other wireless signals.

The foregoing detailed description of the technology herein has been presented for purposes of illustration and description. It is not intended to be exhaustive or to limit the technology to the precise form disclosed. Many modifications and variations are possible in light of the above teaching. The described embodiments were chosen in order to best explain the principles of the technology and its practical application to thereby enable others skilled in the art to best utilize the technology in various embodiments and with various modifications as are suited to the particular use contemplated. It is intended that the scope of the technology be defined by the claims appended hereto. 

1-21. (canceled)
 22. A method for monitoring an asynchronous transaction, comprising: receiving, by an agent executing on a serve, a selection of a back-end calling method to monitor; determining whether the received selection of the method to monitor is an asynchronous method; responsive to the determining, instrumenting the asynchronous method call to monitor; responsive to the instrumenting, monitoring, by the agent, asynchronous framework initiated by the instrumented asynchronous method call; obtaining asynchronous framework data based on the monitoring; and correlating the back-end calling method with a distributed business transaction performed at least in part on the server.
 23. The method of claim 22, wherein the instrumenting includes performing byte code instrumenting.
 24. The method of claim 22, wherein the instrumenting includes injecting intermediate language and a map into a .NET framework.
 25. The method of claim 22, wherein correlating includes: using the obtained asynchronous framework data to correlate threads handling the asynchronous method and a task object executed as part of the asynchronous method.
 26. The method of claim 22, wherein the monitoring the asynchronous framework includes: detecting a task object associated with the asynchronous method; and instrumenting the task object.
 27. The method of claim 26, further comprising: correlating different threads associated with the asynchronous business transaction using the task object instrumentation.
 28. The method of claim 27, wherein the correlating different threads associated with the asynchronous business transaction using the task object instrumentation includes: using an identifier associated with a call sent by the task object to the back-end obtained from the different threads associated with the asynchronous business transaction.
 29. A non-transitory computer readable storage medium having embodied thereon a program, the program being executable by a processor to perform a method for monitoring an asynchronous transaction, the method comprising: receiving, by an agent executing on a serve, a selection of a back-end calling method to monitor; determining whether the received selection of the method to monitor is an asynchronous method; responsive to the determining, instrumenting the asynchronous method call to monitor; responsive to the instrumenting, monitoring, by the agent, asynchronous framework initiated by the instrumented asynchronous method call; obtaining asynchronous framework data based on the monitoring; and correlating the back-end calling method with a distributed business transaction performed at least in part on the server.
 30. The non-transitory computer readable storage medium of claim 31, wherein the instrumenting includes performing byte code instrumenting.
 31. The non-transitory computer readable storage medium of claim 31, wherein instrumenting includes injecting intermediate language and a map into a .NET framework.
 32. The non-transitory computer readable storage medium of claim 31, wherein correlating includes: using the obtained asynchronous framework data to correlate threads handling the asynchronous method and a task object executed as part of the asynchronous method.
 33. The non-transitory computer readable storage medium of claim 31, wherein the monitoring the asynchronous framework includes: detecting a task object associated with the asynchronous method; and instrumenting the task object.
 34. The non-transitory computer readable storage medium of claim 33, the method further comprising: correlating different threads associated with the asynchronous business transaction using the task object instrumentation.
 35. The non-transitory computer readable storage medium of claim 34, wherein the correlating different threads associated with the asynchronous business transaction using the task object instrumentation includes: using an identifier associated with a call sent by the task object to the back-end obtained from the different threads associated with the asynchronous business transaction.
 36. A system for monitoring a business transaction, comprising: a processor; a memory; and one or more modules stored in memory and executable by a processor to perform operations including: receive, by an agent executing on a serve, a selection of a back-end calling method to monitor; determine whether the received selection of the method to monitor is an asynchronous method; responsive to the determination, instrument the asynchronous method call to monitor; responsive to the instrumenting, monitor, by the agent, asynchronous framework initiated by the instrumented asynchronous method call; obtain asynchronous framework data based on the monitoring; and correlate the back-end calling method with a distributed business transaction performed at least in part on the server.
 37. The system of claim 36, wherein the one or more modules are configured to instrument by performing byte code instrumenting.
 38. The system of claim 36, wherein the one or more modules are configured to instrument by including inject intermediate language and a map into a .NET framework.
 39. The system of claim 36, wherein the one or more modules are configured to correlate including: use the obtained asynchronous framework data to correlate threads handling the asynchronous method and a task object executed as part of the asynchronous method.
 40. The system of claim 36, wherein the one or more modules are executable to monitor the asynchronous framework including: detect a task object associated with the asynchronous method; and instrument the task object.
 41. The system of claim 40, wherein the one or more modules are executable to correlate different threads associated with the asynchronous business transaction using the task object instrumentation.
 42. The system of claim 41, wherein the one or more modules are executable to correlate the different threads associated with the asynchronous business transaction using the task object instrumentation including: use an identifier associated with a call sent by the task object to the back-end obtained from the different threads associated with the asynchronous business transaction. 